|
In software development, a rolling release or rolling update development model refers to a continually developing software system; this is instead of a standard release development model which uses software versions that must be reinstalled over the previous version. Rolling release development models are one of many types of software release life cycles and, in terms of software development methodology in general, rolling release development models are less common than standard release development models in most mainstream software sectors, such as operating systems. Although a rolling release model can be used in the development of any piece or collection of software, it is typically seen in use by a minority of Linux distributions. Software distributions, of which Linux distributions form a sizable proportion, are commonly referred to as ''distros'', with rolling release distributions commonly referred to as ''rolling distros''. When used as an adjective, instead of a noun, ''rolling release'' is often shortened to ''rolling'', when referring to distributions, software, or development models. A rolling release is typically implemented using small and frequent updates. However, simply having updates does not automatically mean that a piece of software is using a rolling release cycle; for this, the philosophy of developers must be to work with one code branch, versus discrete versions. When the rolling release is employed as the development model, software updates are typically delivered to users by a package manager on the user's personal computer, accessing through the internet a remote software repository (often via a download mirror) stored on an internet file server. Not all software distributions based on, derived from, or related to rolling release distributions are necessarily rolling releases themselves. An example of this is ConnochaetOS (formerly DeLi Linux), which is a ''standard'' release distribution based on the rolling release distribution Arch Linux. Similarly, most of the software contained in a rolling distribution's software stack is usually standard release. The remainder of this article focuses on the rolling release model as applied to software distributions (versus software applications). From this point onwards, unless otherwise stated, the term ''rolling release'' will be taken to refer to distributions and ''not'' to software in general. ==Development models== For the purpose of this article, rolling releases have been divided into the categories ''partially rolling'' (see ''part-rolling''), ''fully rolling'' (see ''full-rolling''), ''truly rolling'' (see ''true-rolling'') and its pseudo-opposite (see ''pseudo-rolling''), ''optionally rolling'' (see ''opt-rolling''), and ''cyclically rolling'' (see ''cyclic-rolling''). The terms ''partially rolling'' and ''partly rolling'' (along with synonyms ''semi-rolling'' and ''half-rolling''), ''fully rolling'', ''truly rolling'' and ''optionally rolling'' are all standard terms used by software developers and users.〔(【引用サイトリンク】title=half-rolling development model )〕〔(【引用サイトリンク】title=The Chakra Project Wiki: FAQs )〕〔(【引用サイトリンク】url=https://fedoraproject.org/wiki/Release_Lifecycle_Proposals )〕〔(【引用サイトリンク】url=https://lists.fedoraproject.org/pipermail/devel/2010-March/132434.html )〕〔(【引用サイトリンク】title=Linux Certification – Preparation )〕〔(【引用サイトリンク】url=http://en.opensuse.org/openSUSE:Why_openSUSE )〕 However, the term ''cyclically rolling'' is not necessarily a standard term, though the term ''cyclic release'' is — see ''Types of non-rolling releases''. The term ''cyclically rolling'' (and ''cyclic-rolling'') has been used in this article to differentiate rolling releases based on a ''cyclical'' (versus ''rolling'') development branch of a non-rolling distribution, since these (along with pseudo-rolling releases) have relevant differences, from other types of rolling releases — see freeze (software engineering) and ''Types of rolling releases'' subsection below. As a pseudo-opposite to ''truly rolling'' (or ''true-rolling''), the term ''pseudo-rolling'' is used by some users to describe and distinguish distributions such as aptosid, Aurora OS, antiX and LMDE, among others, which are based on (usually a development branch of) a non-rolling distribution which is modified to provide the end-user with a user experience approximating that of a true rolling release. For brevity, ''partially rolling'', ''cyclically rolling'', ''truly rolling'', ''optionally rolling'' and ''fully rolling'' have been contracted to ''part-rolling'', ''cyclic-rolling'', ''true-rolling'', ''opt-rolling'' and ''full-rolling'', respectively, in some parts of this article. The contraction of these terms is not necessarily standard nomenclature, or a reflection of general use within the software community, and is used merely as a convenient shorthand for the purposes of this article. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「rolling release」の詳細全文を読む スポンサード リンク
|